-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(cwl): Add metric definitions for LiveTail #916
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@@ -1297,6 +1297,11 @@ | |||
"type": "boolean", | |||
"description": "Whether the user has access to CodeWhisperer Chat" | |||
}, | |||
{ | |||
"name": "hasLogEventFilterPattern", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is over-specific. Can you find a field name that will be useful for other metrics in the future, e.g. hasPatternFilter
(why is "log event" important enough to call out in the field name?)
Another way of future-proofing is to use enum-like (or string) fields instead of booleans. It's pretty cumbersome that we have booleans for each of these variants, and may need to add even more in the future.
"name": "hasLogEventFilterPattern", | ||
"type": "boolean", | ||
"description": "If LogEvent filter pattern is applied" | ||
}, | ||
{ | ||
"name": "hasTextFilter", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How is hasLogEventFilterPattern
different than this existing field?
@@ -4995,6 +5010,48 @@ | |||
} | |||
] | |||
}, | |||
{ | |||
"name": "cwlLiveTail_Start", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am certain that we have existing cloudwatch metrics. Yet these new "live tail" metrics don't use the same prefix, so now both will be harder to discover.
Problem
Cloudwatch wants to monitor usage metrics of the LiveTail integration
Solution
When starting a session emit telemetry for:
When closing a session:
License: I confirm that my contribution is made under the terms of the Apache 2.0 license.